Description of Change

Created the Radio button component. Given the extreme similarities to Checkbox/Checkbox group, this involved pulling out a shared component (CheckboxRadio) to have shared code under the hood and basically just conditionally swap the icon. Then Radio button itself was formed off modifying Checkbox group so only one would be selected.

Testing Packages

• 0.27.2-alpha.1
• 0.27.2-alpha.0

Screenshots/Video

iOS: Not recorded in Storybook because ExpoGo app was updated and, unlike Android, there's no way to install an older version so it's out of commission until we update dependencies to the newer SDK.

Android:

Web:

Flagship (iOS):

Flagship (Android):

Testing

Smoke tested nothing appeared to break with existing Checkbox/Checkbox group with the transition to shared underlying component with Radio.

Validated Radio button appeared to be behaving as expected in Web/iOS/Android (including iOS/Android in flagship). One bug noted with VoiceOver (iOS) only where it intermittently (more often than not, but not always) when activating a different radio will read out that it is unselected then immediately read out again that it is selected; bug #596 created.

• Tested on iOS
• Tested on Android
• Tested on Web

PR Checklist

Code reviewer validation:

• General
  • PR is linked to ticket(s)
  • PR has changelog label applied if it's to be included in the changelog
  • Acceptance criteria:
    • All satisfied or
    • Documented reason for not being performed or
    • Split to separate ticket and ticket is linked by relevant AC(s)
  • Above PR sections adequately filled out
  • If any breaking changes, in accordance with the pre-1.0.0 versioning guidelines: a CU ticket has been created for the VA Mobile App detailing necessary adjustments with the package version that will be published by this ticket
• Code
  • Tests are included if appropriate (or split to separate ticket)
  • New functions have proper TSDoc annotations

Publish

If changes warrant a new version per the versioning guidelines and the PR is approved and ready to merge:

• Merge main into branch
• Merge branch to main
• Verify that Check Component Integrations workflow ran successfully
• Publish new version after merging